|
The Governance Scope regulates the governance processes and balance of power of the Sky Ecosystem. The Governance Scope must ensure that the resilient equilibrium of Sky Governance remains protected against all potential direct and indirect threats.
View Provenance
This Article regulates the Weekly Governance Cycle which comprises two distinct subsets, the Operational Weekly Cycle and the Atlas Edit Weekly Cycle.
View Provenance
This Section defines the Operational Weekly Cycle, a predictable weekly framework for recurring operational decisions. The Operational Weekly Cycle is implemented via Governance Polls and Executive Votes. The Cycle complements the Monthly Governance Cycle by enabling recurring weekly decisions to be made that require quicker action than is allowed by the Monthly Governance Cycle.
Supporting Documents
The subdocuments herein contain essential definitions pertinent to the Operational Weekly Cycle.
An Executive Vote (also “Executive”) is a formalized governance proposal that requires on-chain voting. Through the Executive Vote mechanism, SKY holders steward Sky Governance by voting on Executive proposals that pertain to operations maintaining the Protocol. Executive Votes execute technical changes to the Sky Protocol.The Executive Vote occurs approximately every two weeks. Its contents are often determined by weekly Governance Polls that pre-approve the inclusion of proposals in the Executive Vote. However, the Atlas can explicitly authorize proposals to go directly to an Executive Vote.Note that the terms ‘Executive’ and ‘spell’ are distinct concepts. The term ‘Executive’ or ‘Executive Vote’ is used in all instances where the formal governance vote is being referenced. The term ‘Executive Process’ refers to the end-to-end process of the development of an Executive Vote, in which Facilitators, spell teams (also referred to collectively as the “Governance Security Engineering Team”) and other recognized Ecosystem Actors participate. The term ‘spell’ refers to the smart contract that executes the changes to the protocol approved by Sky Governance in an Executive Vote. Generally, when referring to spell team operations and their technical outcome or product (including code base, code operations, code reviews and code quality), the term ‘spell’ will be used. The term ‘spell process’ refers to the end-to-end process of developing a spell, a process in which the Governance Facilitators and the current spell team participate. The term ‘spell development process’ is a subset of the ‘spell process’ and pertains solely to the technical development of the spell by the current spell team.